084932114X by Unknown

084932114X by Unknown

Author:Unknown
Language: eng
Format: epub
Published: 2006-08-07T01:40:38+00:00


128 Lightweight Enterprise Architectures

xt Map

Sample Conte

e 7.1

Figur

Execution Architecture

129

Figure 7.2

Sample Logistical Diagram

opment can change these initial assumptions, as they are only guide considerations for the project resources to build upon.

PROJECT VISION

The last set of primary responsibilities for the architects in the Execution Architecture is the development of the project vision. This is the beginning of how the project needs to evolve for the Technology Roadmap realization. Ultimately, this is the initial idea for the design of the project. There are three primary areas of focus within the development of the project vision:

1. Impacted systems

2. Potential solutions

3. Key business logic

To best develop the project vision, first the architect must understand the relationship of this project to the current systems in the enterprise, discover what type of solutions are applicable, and then identify the key business logic the solution must provide.

Impacted Systems

The impacted systems have already become familiar to the architects, as the previous diagramming responsibilities should have identified many of the systems impacted. In addition, systems that have been identified also need assessment on how this solution affects these current systems in the organization. This requires the identification of key resources for these systems and discussing the design plans of the project with these resources.

130 Lightweight Enterprise Architectures

While there is not a specific approach or format to proceed on these tasks, the architect needs to meet and have discussions with as many of these resources as possible. The input of these resources will be invaluable and this is an excellent beginning to gaining buy-in. These key resources can affect the success of the project. In addition, these resources also can provide potential insight into the project vision.

Potential Solutions

An additional area of responsibility within the project vision is the discovery of potential solutions that can offer the needed functionality to the enterprise. Identifying a list of candidates for the project provides a list that can:

Modify a current system

Provide internal custom development

Find an external solution

A combination of the above

The goal of the architect in this area is not to restrict to a single solution, but rather identify a short list of candidates that the pr oject resources select in their initial activities. Finally, in the potential solutions, there is identification of the possible candidates, which includes some due diligence of why these solutions made the short list for this project.

If the solution is clear and only a single choice is appropriate (this must be definite), then this effort only requires a verification of resources on the selected solution. However, the goal of the potential solution is to clear the path for the project team to quickly come to a selection on the solutions.

Key Business Logic

Finally, the architect must determine what functionality the solution provides and the critical business practices that characterize how the organization operates. These components comprise the key business logic and are important for capturing the initial scope of the solution. In addition, this provides the criteria for selecting the right choice from the previous activities captured in the potential solutions.

Together, the



Download



Copyright Disclaimer:
This site does not store any files on its server. We only index and link to content provided by other sites. Please contact the content providers to delete copyright contents if any and email us, we'll remove relevant links or contents immediately.